-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
fix(integrations): update usage of is_enabled data forwarding #103584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
❌ 2 Tests Failed:
View the top 2 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
leeandher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, may just want a test for the new models to prevent a regression
src/sentry/integrations/api/serializers/rest_framework/data_forwarder.py
Show resolved
Hide resolved
tests/sentry/integrations/api/endpoints/test_data_forwarding.py
Outdated
Show resolved
Hide resolved
| ) | ||
| for project_id in project_ids | ||
| ] | ||
| ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Update without project_ids deletes all enrolled projects
The update method always processes project_ids from validated_data, but this field now has a default value of an empty list when not provided in the request. When updating a data forwarder's main config without explicitly providing project_ids, the serializer will use the default empty list, causing the code to delete all enrolled project associations. The method should only modify project_ids if they were actually present in the request data.
ECO 1200 and ECO 1269